Preparation of a Three-Dimensional Model for Data Transmission

ABSTRACT

Various embodiments include a method for preparing a three-dimensional model for a fabrication component in the context of production for data transmission to different receiving entities comprising: receiving three-dimensional model data via an input interface; providing a detail-state for processing of the three-dimensional model on the respective receiving entity; and executing a reduction algorithm on a reference version of the received three-dimensional model data for automatically calculating and providing a reduced reference version with the provided detail-state.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a U.S. National Stage Application of InternationalApplication No. PCT/EP2019/060549 filed Apr. 25, 2019, which designatesthe United States of America, and claims priority to EP Application No.18171518.6 filed May 9, 2018, the contents of which are herebyincorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates to three-dimensional modeling. Variousembodiments may include methods, reduction modules, and/or computerprograms for providing different versions of a three-dimensional modelfor use in production.

BACKGROUND

Computer aided systems (CAD systems) provide electronic support inengineering industry. CAD is mainly used for detailed engineering bymeans of three-dimensional models (in this application also abbreviatedas ‘3D model’) of physical components, but it is also used throughoutthe engineering process from conceptual design and layout of products,through strength and dynamic analysis of assemblies and for generatingmeasurement programs and quality features for measurement devices todefinition of manufacturing methods of components.

In the course of production of a technical component or system, it isoften necessary to exchange 3D model information between differentparties, e.g. product development, clients, or different user groupsamong others. However, this data exchange involves a considerablesecurity risk, because the different parties require different securitylevels; for example, in development engineer needs to have allinformation and a high level of detail of the 3D model, whereas a clientonly requires a part of the 3D model data and generally requires a lowerlevel of detail.

Thus, the 3D data model should not be exchanged in the same manner fordifferent receiving nodes or parties in order to comply with securitystandards. In known systems, it therefore necessary to manually adaptthe 3D model before intented data exchange to other entities. Inparticular, critical data in the model are deleted by hand one after theother. This approach is cumbersome and error prone.

SUMMARY

The teachings of the present disclosure include an improved approach toprepare 3D data models for data transmission to a plurality of receivingentities, which differ in their requirements with respect todetailedness of model data. In particular, the security of the dataexchange of 3D model data should be increased. For example, someembodiments of the teachings herein include a method for preparing athree-dimensional model (m) for a fabrication component in the contextof production for data transmission to different receiving entities (C),comprising the following steps: receiving (S1) three-dimensional modeldata (m) via an input interface (i1); providing (S2) a detail-state forprocessing of the three-dimensional model on the respective receivingentity (C); and executing (S3) a reduction algorithm (X2) on a referenceversion (m′) of the received three-dimensional model data (m) forautomatically calculating and providing (S4) at least one reducedreference version (rm′) with the provided detail-state.

In some embodiments, the detail-state is provided specifically for eachreceiving entity (C) and wherein providing (S3) comprises: receiving(S21) context data (cd) specifying in which technical context thethree-dimensional model (m) will be used for processing on the receivingentity (C); and accessing (S22) a rules engine (RE) with an associatedrules database (RDB) with the received context data (cd) in order toprovide the detail-state algorithmically, indicating a respective levelof detail in which the reduction algorithm (X2) should be operated with.

In some embodiments, the reduction algorithm (X2) deletes, adds and/ormodifies determined elements in the reference version (m′) of the 3Dmodel based on the provided detail-state, wherein all references to thedetermined elements are deleted, too.

In some embodiments, the method further comprises storing (S5) thereduced reference version (rm′) of the 3D model with a digital referenceto the 3D model (m).

In some embodiments, the context data (cd) specify a context and/or afunctionality in which the 3D model is intended to be used on thereceiving entity (C), in particular a process step and/or an assemblystep during production and/or assembly.

In some embodiments, the reduced reference version (rm′) is prepared forbeing provided on smart glasses (ARG) of a receiving entity (C).

In some embodiments, the method is executed in a batch mode in a centralmanagement system (PLM) and/or in a local application (CAD).

In some embodiments, the reduced reference version (rm′) is comparedwith the three-dimensional model (m).

In some embodiments, the method is executed in a CAD system (CAD) andwherein the input interface (i1) is an API interface of the CAD-systemwhich may access a second set of functions (F2) of the CAD system (CAD).

As another example, some embodiments include an eduction module forpreparing a three-dimensional model (m) for a fabrication component inthe context of production for data transmission to different receivingentities (C), comprising: an input interface (i1) for receiving 3D modeldata (m); and a processor (P) for providing a detail-state of areceiving entity (C) for processing the three-dimensional model andwherein the processor (P) is further adapted to execute a reductionalgorithm (X2) on a reference version (m′) of the received 3D model data(m) for automatically calculating and providing at least one reducedreference version (rm′) thereof with the provided detail-state.

As another example, some embodiments include a computer program withprogram code for executing a method as described herein, if the computerprogram is executed on an electronic device (100, P, CAD).

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description of the figures uses the drawings todiscuss illustrative embodiments, which are not to be construed asrestrictive, along with the features and further advantages thereof. Inthe drawings:

FIG. 1 shows a schematic representation of a reduction module forpreparing a 3D model to be transmitted to a plurality of clients withdifferent detail-states in an exemplary embodiment incorporatingteachings of the present disclosure;

FIG. 2 is an alternative embodiment of the reduction module depicted inFIG. 1;

FIG. 3 shows the reduction module for preparing a 3D model fortransmission to different clients in more detail;

FIG. 4 is a flow chart of a method according to an example embodimentincorporating teachings of the present disclosure;

FIG. 5 represents an example embodiment and an application withaugmented reality glasses; and

FIG. 6 is a flow chart of a possible sequence of algorithmic executionsaccording to an example embodiment incorporating teachings of thepresent disclosure.

DETAILED DESCRIPTION

Some embodiments of the teachings herein include a method for preparinga three-dimensional (3D) model—to be used for a fabrication component inthe context of production—for data transmission to different receivingentities. The receiving entities differ in their respective securityrequirements. For example, a first entity (e.g. a developer client)needs to be provided with all of the 3D model data and thus a highdegree of detailedness, whereas a second entity (e.g. a service client)only needs to be provided with less data and thus with a low degree ofdetailedness. The different levels of detailedness are represented in aso-called detail-state. In some embodiments, a method comprises thefollowing steps:

-   -   Receiving 3D model data of an (original) 3D model via an input        interface, which may be provided as API interface of a CAD        system;    -   Providing a detail-state for processing of the three-dimensional        model on the respective receiving entity. The detail-state        represents the requirements of the respective receiving entity        with respect to detailedness of the model to be processed;    -   Executing a reduction algorithm on a reference version of the        received 3D model data for automatically calculating at least        one reduced reference version (being related to the received 3D        model data) in the provided detail-state; and    -   Providing the reduced reference version of the 3D model for data        transmission to the respective receiving entity.

In some embodiments, a method automatically prepares different securityversions or derivations as so called reduced reference versions of anoriginal 3D model which are intended to be transferred to differentreceiving entities, wherein the different receiving entities do havedifferent security requirements. This has the technical advantage, thatthe reduced reference versions may be calculated beforehand in apreparation phase so that data transmission to the client entity may beexecuted much more faster and safer. There is no longer a need formanual adaption of the 3D model data. Further, one specific reducedreference version is selectively dedicated to and provided for areceiving entity. Thus, each receiving entity has its own reducedreference version it is provided with.

For calculating or computing the reduced reference versions,instructions are generated that are compatible with the applicationprogramming interface (API) of a CAD software system which is used totransmit the instructions to a kernel of the CAD system. The kernelprovides calculation functionalities. The kernel provided CADfunctionalities are assessed by the instructions to calculate thereduced reference versions. The calculated reduced reference versionsare linked to and/or refer to the original 3D model (storage address ina memory).

In some embodiments, the detail-state is provided dedicatedly for aspecific receiving entity or a group thereof (e.g. a group of receivingentities which have the similar functionality and similar or the samesecurity requirements) and wherein the step of providing thedetail-state comprises:

-   -   Receiving context data specifying and representing in which        technical context the receiving entity (e.g. development,        service) will use the reduced version of the 3D model; and    -   Accessing a rules engine and/or a rule database with the        received context data in order to algorithmically deduce and        provide the detail-state of the receiving entity, indicating        requirements for a respective level of detail, according to        which the reduction algorithm should be operated with. The        context data are processed by means of executing a requirement        algorithm in order to automatically calculate the detail-state        from the context data. The requirement algorithm processes as        input the context data and provides as output a set of        requirements with respect to the detailedness of the model. This        has the technical advantage that the regulations and provisions        for calculation of the detail-state (i.e. the rules to calculate        the detail-state) may be amended independently of the sending or        receiving system and even during execution of the method.

In some embodiments, the detail-state is automatically calculated byprocessing affiliation data of the respective receiving entity. Theaffiliation data may thus indicate an affiliation to a functionalprocessing group (e.g. the group of receiving entities which are adaptedfor the integration and fitting of a technical component during thecourse of production or attachment of the component to othercomponents). In case the receiving entity is a client device (e.g. aclient computer), client group data or user group data might beprocessed for providing the detail-state (e.g. all clients in adeveloping group need to be provided with a high degree of detailednessof the 3D model, whereas each client in an assembly group only need tobe provided with a lower degree of detaildness, which may be specificfor a single process step.

In some embodiments, the reduction algorithm deletes, adds, and/ormodifies determined elements in a reference version of the (original) 3Dmodel—and thus in a reference copy of the received 3D model data—basedon the provided detail-state, wherein all references to the determinedelements are deleted, too. The determined elements (i.e. the elements inthe 3D model data, which need to be deleted or made unreadable) may beidentified by means of an indication in the detail-state. The reductionalgorithm does not only delete model parts or elements, but may alsonewly generate additional elements, like e.g. adding a new layer andadding 3D units to the new layer. Further, the reduction algorithm mayrename models and model parts and/or generate different formats for themodel (step, STL, IGS etc.). The reduction algorithm may also amend andchange the model or parts thereof.

In some embodiments, the method further comprises:

-   -   Storing the reduced reference version of the 3D model with a        digital or electronic reference to the (original, unamended) 3D        model. This has the technical advantage that all model        amendments (reductions) and all the different reduced model        versions are trackable. In some embodiments, meta data of the        model reduction (execution of the reduction algorithm) are        detected and stored so that every model amendment is transparent        and traceable. The reference may be provided as a link (url        link). For providing the link, a PDM/PLM system may be used        (PLM: Product lifecycle management, PDM: Product Data        Management). In some embodiments, an invalidation process may be        implemented and provided that makes sure that all derivations of        the original model—and thus all reduced reference versions of        the original model—will automatically become invalid (and will        automatically be invalidated) if the original model has been        changed. In some embodiments, an adaption algorithm may be        provided, which adapts all reduced reference versions        (derivations) of the original model, which has been changed        according to these changes. Thus, if the original model will be        changed, then it is assured that automatically all derived or        dependent models will be changed accordingly, too.

In some embodiments, the context data specify a context and/or afunctionality in which the 3D model is intended to be used on thereceiving entity and in particular a process step, in particular anassembly step, during development, production and/or assembly (of atechnical or physical component in a complex system, e.g. a machine orthe like). As an advantage, the process step is decisive for calculationof the detail-state. Thus, the provisioning (calculation) of thedetail-state is based on additional parameters which indicate a usage orapplication of the 3D model.

In some embodiments, the reduced reference version is prepared for beingprovided (transmitted) on smart glasses, comprising augmented reality(AR) glasses or virtual reality (VR) glasses. Smart glasses are wearablecomputer glasses that add information alongside or to what the user seesduring his work on the technical component (e.g. during assembly).Superimposing 3D model information onto a field of view is achievedthrough an optical head-mounted display (OHMD) or embedded wirelessglasses with transparent heads-up display (HUD) or augmented reality(AR) overlay that has the capability of reflecting projected digitalimages as well as allowing the user to see through it, or see betterwith it (e.g. by providing annotations with respect to the technicalcomponent, like which tools are necessary to assembly the component inthe system or on which exact position the component is to be placed).Smart glasses may utilize cellular technology or Wi-Fi. In someembodiments, modern smart glasses may be equipped with effectivewearable computers which can run self-contained mobile apps, inparticular the model detailing application or a client version of thesame in order to provide the reduced reference version of the 3D modellocally on the smart glasses. In some embodiments, the smart glasses arehandsfree that can communicate with the Internet via natural languagevoice and/or gesture commands. Optionally, touch buttons may be used.

The reduced reference version data may be prepared to be transmitteddirectly to the smart glasses or indirectly, namely may be firstlytransmitted to a receiving client device, e.g. a mobile device and/or abeamer et cetera and secondly from the receiving client device to theassociated smart glasses. This feature makes production more flexible inthat the necessary reduced reference version of the 3D model is providedlocally on-site and directly at a location, where the user is workingand processing on the component. As a major technical advantage, onlythose data are to be transmitted to the local site (e.g. smart glassesor client computer of the receiving device) which are relevant in thatprocessing step during production. Thus, only a small selection of dataneeds to be transmitted to the receiving entity which has the advantagethat standby time and waiting periods for generation of thevisualization may be reduced significantly.

In some embodiments, the method is executed in a batch mode in a centralmanagement system (e.g. a product lifecycle management system—PLM) or ina local application (computer aided design system—CAD). This has theadvantage that the automatic preparation of the reduced 3D models fortransmission may be automated still further, which in the end reducesfailure sources and helps to accelerate assembly. The method may beexecuted as a computer application, which may be hosted on differentsystems (e.g. centrally/PLM or locally/CAD).

In some embodiments, the (calculated) reduced reference version may becompared with the original 3D model for further analysis (first level ofcomparison: comparing original model with derived model). The result ofthis comparison is stored. Again, the result of this comparison may—in asecond level of comparison—be compared with other comparison results forother versions. This comparing step may be executed by using functionsfrom the CAD system. Thus, a two level comparison may be implemented forthe derived models and its depending comparison results.

Advantages, features, and example embodiments which have been describedwith respect to the method, may equally be applied to the proposedsolution according to the apparatus or reduction module and vice versa.Respective functional features (e.g. comparing with the original 3Dmodel) are deployed in functional modules, which are adapted to executethe respective function (in the example, given above, a comparatormodule), wherein the modules are to be construed as software modulesand/or hardware modules to be executed in a computing entity.

In some embodiments, there is a reduction module for preparing athree-dimensional (3D) model for data transmission to differentreceiving entities. The 3D model is used for a fabrication component inthe context of production. As already mentioned above, the receivingentities differ in their respective security requirements and thereforeneed to be provided with different levels or degrees of detailedness.Thus, detail-state specific versions of a three-dimensional model areautomatically pre-calculated. In some embodiments, the reduction modulecomprises:

-   -   An input interface for receiving 3D model data, which may        preferably be provided as application programming interface of a        CAD system; and    -   A processor for providing a detail-state for processing the        three-dimensional model on the respective receiving entity. The        processor is further adapted to execute a reduction algorithm on        a reference version of the received 3D model data for        automatically calculating and providing at least one reduced        reference version with the provided detail-state.

The reduction module may relate to a computer program product with acomputer program stored thereon. The computer program is adapted toexecute the methods described above. The computer program product may orcomprise a computer readable storage medium.

In some embodiments, there is an application or computer program,tangibly embodying a program of machine-readable instructions executableby a digital processing apparatus to perform the preparation method withthe reduction algorithm described above, if the application or programis executed on the digital processing apparatus device (e.g. in acentral administration system, like a product lifecycle managementsystem or in a central or local CAD system). In particular, theapplication refers to a model detailing application, which is adapted toprovide the 3D model in the reduced level of detail, required by thespecific client or receiving entity. Thus, the method may be provided asa computer program with program code for executing the preparationmethod, mentioned above, if the computer program is executed on anelectronic device (inter alia a PLM system or CAD system). Thepreparation method preferably uses the CAD system and more specificallyfunctions of the CAD kernel.

In some embodiments, the reduction algorithm is based on functions ofthe CAD kernel. Moreover, the step of comparing the derived (reduced)versions with the original model is based on functions of the CADkernel, too. For this reason, the CAD system needs to be started orneeds to be assessed via an API interface with special instructions. Thefunctions to be executed by the CAD system may be operated (executed) asa hidden service according to the instructions provided by thepreparation method or by the modelling detailing application. Theinstructions serve to calculate reduced versions of the 3D model in theprovided detail-state, to analyze versions of the 3D model, to amendand/or store versions, to aggregate different versions and/or to addcontext data and/or meta data to the 3D model data.

In the following a short definition of terms is given. Generally, theproposed solution may be used in the context of production, sales (e.g.for configuration), analysis, product assembly, quality and serviceprocesses for technical products.

A 3D model (three-dimensional model) is a mathematical representation ofany surface and/or structure of an object in three dimensions viaspecialized software, especially CAD system software. The CAD system mayonly be accessed via an application programming interface (API) and notvia the (normal) user interface thereof to access the CAD kernel withrespective functionality. The product is called a 3D model. The modelmay thus represent a technical or physical object or body (in particulara component to be integrated in a technical system or machine) using acollection of points in 3D space, connected by various geometricentities such as triangles, lines, curved surfaces, etc. Being acollection of digital data (or an electronic dataset), comprisinggeometric data of the component and/or structural data, referring to thecomposition of matter and/or to the attachment requirements of thecomponent, 3D models are typically created algorithmically (proceduralmodeling) or scanned. Their surfaces may be further defined with texturemapping procedures for applying different surface structures. 3D modelsare widely used in engineering, production, e.g. in CAD systems. The 3Dmodel data represents the respective 3D model and may be construed in asimilar manner.

Receiving entity may be a computer-based entity of a client. Typically,several local clients may be connected via a network (wired or wireless)to a central computer entity (e.g. a PLM-System or a CAD system), whichmay be adapted to manage the data to be provided for the connected localclients. A receiving entity, may, for example, be a CAD system. A clientmay comprise more than one receiving entity. The receiving entitiesdiffer in their technical context and functionality and thus in theirsecurity level. In a preferred embodiment the receiving entity comprisessmart glasses, like AR glasses.

The detail-state is an electronic dataset which defines the requirementsof the respective client for detailedness of the 3D model. Thedetail-state refers to a specific client/receiving entity or to a groupthereof (e.g. receiving entities with same or equal functionality). Thedetail-state may be calculated and provided on an external instance andmay be read in by the model reduction application or it may becalculated on the respective computing entity which is also responsiblefor processing the model reduction application and for providing thereduced 3D model. The detail-state may be provided, by:

-   -   Receiving context data from the receiving entity of the client,        specifying in which technical context (e.g. development,        service) the 3D model will be used; and    -   Accessing a rules engine or a rule database with the received        context data in order to provide the detail-state, indicating        requirements for a respective level of detail. Providing the        detail-state may be based on user group data or data, referring        to the group of receiving entities with associated        functionality. In a technical sense, the functionality of a        receiving entity of a client to process the 3D model is        associated to a certain group of clients.

The detail-state may comprise three different categories:

-   -   Low—e.g. shell geometry for constructional validation;    -   Middle—e.g. model with PMI information and feature information        for CAM programming; and    -   High—e.g. model with additional information, like for a wired        terminal box with detailed information relating to internal        functions. In a high detail-state the 3D model data may comprise        the following parameters: KE (constructional element), PMI        (Product Manufacturing Information), format (e.g. STEP, JT, NX,        CREO, STL, . . . ) and group or process step information        (planer, operator, sales, . . . ).

In a configuration phase additional states may be defined. In someembodiments, the rules engine is modular.

The reduction algorithm refers to an algorithm, executed on a computer.The reduction algorithm deletes, modifies, and/or adds selected elementsin the 3D model based on the provided detail-state, wherein allreferences to the selected elements are deleted, too. The reductionalgorithm needs to access the reference version of the original 3D modeldata and needs to receive a detail-state with requirements with respectto required detailedness of the receiving client, in order to generateand calculate a reduced reference version of the 3D model which isdedicated for the respective client and processing thereon. Thereduction algorithm may be initiated automatically, as soon as the 3Dmodel needs to be transferred to or to be provided on a receivingentity. It may be executed in a batch mode. The reduction algorithmpreferably accesses a rule database, in which rules are stored forcalculating instructions, which particular element(s) in the (original)3D model is (are) to be deleted in which manner (totally or in part,with references to the element be maintained or deleted, etc. and byusing what kind of reduction, like deletion, anonymization orde-identification of the respective element in the 3D model data set).

In some embodiments, the reduction algorithm uses functions of a localcomputer aided design application (CAD application). It uses the API(application programming interface) of the CAD system to access the CADkernel for hidden execution of functions of the CAD application.

The preparation method of the proposed solution may be defined in a highlevel language, like C, C# or C++ and uses the functions of the CADsystem via its API functions. These API functions may access the CADkernel and may thus use all procedures provided by the CAD system toamend the 3D model without using the user interface of the CAD system.This approach makes it possible to also use functions of the CAD systemwhich are not accessible via the (normal) user interface of the CADsystem and thus to execute a function as a ‘hidden service’. This hasthe advantage to extend the functionality of the application software.By using the API functions, the 3D model data are received and may beprocessed (for calculating the reduced reference version of the 3Dmodel) according to the provided detail-state or according to a resultof a rules engine. In some embodiments, the calculated reduced referenceversion of the 3D model is validated in order to assure that thegenerated model derivations are still a valid model.

The reduced reference version of the original 3D model is calculatedautomatically by means of a computer by applying the reductionalgorithm. The reduction algorithm is operated according to thedetail-state. The reduction algorithm may access a rule database forstoring rules, which may be amended independent of the 3D model and ofthe client requirements.

One of the main problems is to handle the provision of technical 3D datafor different clients or receiving entities C in different technicalcontexts (e.g. product development, product assembly, product serviceetc.). Each of the receiving entities may for example have differentfunctions or tasks and therefore needs to be provided with differentparts of the underlying 3D model. Depending on the technical context forprocessing the 3D model, different requirements of the 3D model dataexist with respect to the required level of detail. For example, a firstoperator who is working on a first processing step in productconstruction needs a first set of 3D model data, whereas a secondoperator needs a second set of 3D model data, which may e.g. moredetailed or more general than the first set.

A model detailing application MDA is proposed which serves to provide areduced reference version rm′ of an original 3D model m, based on areference version m′. In this context, therefore, the ‘model detailingapplication MDA’ is a synonym to the ‘method for preparing a 3D model’as claimed. The reduced reference version rm′ is characterized in thatit is a computed derivation of the original 3D model and only comprisesdata in compliance with a provided detail-state. This has the technicaladvantage that security may be improved as on the one hand nounnecessary data will be exchanged and on the other hand by assuringthat the respective client with its functionality and processing contextis provided with the 3D model data it needs and it is allowed to access.

The model detailing application MDA may be used and accessed directly inthe CAD client system or may be provided indirectly via the PLM client.At the PLM client a CAD software needs to be executed in batch mode. Themodel detailing application MDA is adapted to generate derivations of anoriginal (released) 3D model according to the detail-state and accordingto rules, stored and processable in a rules engine RE. The rules may bepre-configured and also may be configured via a user interface UI of themodeling detailing application MDA. The derivation of amended (reducedor enriched) model versions may thus be executed in an efficient andfast manner for each process step of a production process dedicatedly.In some embodiments, a reduced reference version of the 3D model isprepared for each process step separately. Further, the prepared 3Dmodel derivations serve to control the productional process by providingcontrol data for each different process step separately. For example,the respective machine to be used for production in a multi-stepproduction process (e.g. robot, press, welding device etc.) is providedwith the very data it requires (in the examples above: e.g. machineprogram for controlling the robot, force to be applied on the press andtemperature to be applied for welding).

FIG. 1 shows a first example embodiment of the teachings herein in whichthe model detailing application MDA is deployed on a central computingnode 100, which serves to manage a plurality of network connectedreceiving entities C which are computing entities, acting as clients forreceiving the 3D model derivations, computed by the model detailingapplication MDA. In this example, the model detailing application MDA isdeployed on a processor P, which in this example embodiment alsocomprises a user interface UI and a rules engine RE. The rules engine REmay be adapted to calculate instructions ins for controlling functionsto be executed on a CAD system CAD for serving the model detailingapplication MDA with a result in the form of a calculated reducedreference version rm′ of the original model m. The receiving entities(also called clients) C are connected to the model detailing applicationMDA via a network NW. The computing node 100 may be adapted to provide aproduct lifecycle management application PLM, which is adapted todistribute the data. In the example implementation, shown in FIG. 1, thePLM application may also be provided as external instance or computingnode, which is connected to the MDA application via respectiveinterfaces.

The model detailing application MDA may be deployed on the computingnode 100 or even within the product lifecycle management applicationPLM. The model detailing application MDA may also be deployed within theCAD system.

The model detailing application MDA prepares the reduced referenceversion rm′ for transmission to the respective client (and thus for therespective receiving entity or node C). The computing node 100 and theclient may be connected via a secured network NW. The network NW may bea wired or a wireless network. The reduced reference version rm′ is aderivative of the original model m and may in particular be a reducedform, an amended form or even an enriched form of the original model m.The derivatives are administered centrally by means of the PLM—and/orCAD system. The derivatives are linked to the original model m formaking the changes traceable and processable.

The model detailing application MDA is adapted to calculateinstructions, in FIG. 1 referenced with ‘ins’, for controlling functionsin the CAD system. The instructions ins are calculated based on rules,which are stored in a rules database RDB. The rules are applied in therules engine RE for computing the instructions ins by considering theprovided detail-state.

The model detailing application MDA uses a set of functions F1, F2 ofthe CAD system CAD. It uses the API (application programming interface)to transmit instructions ins, prepared by the model detailingapplication MDA, to the CAD system. The CAD system comprise a (normal)user interface UI_(CAD) for assessing a first set of functions. Via theapplication programming interface API of the CAD system, it is, howeverand in addition, possible to access the CAD kernel for hidden executionof a second set of functions F2 of the CAD application, which are notaccessible via the normal user interface UI_(CAD). The set of functionsF1, F2 are controlled with instructions ins, computed by the modeldetailing application MDA in order to calculate the reduced referenceversion rm′, which is transmitted via the model detailing applicationMDA to the respective clients C.

FIG. 2 shows another example embodiment, in which the model detailingapplication MDA is implemented or deployed in a computer aided designsoftware module CAD. The CAD system is adapted to be processed on theprocessor P, which may be deployed in the computing node 100 (server).In this embodiment, the original 3D model is received locally on thecomputing node 100, but only the reduced reference version rm′ of theoriginal model m will be processed and provided on a user interface. Inorder to improve security, it may be assured that only the reducedreference version rm′ will be made accessible (and not the originalmodel m). The reduced reference version rm′ may be provided to the PLMsystem PLM for distribution to the clients C.

FIG. 3 shows the model detailing application MDA in more detail. Themodel detailing application MDA is a computer application or program andmay be deployed on a computing system centrally or locally. It receiveselectronic input data via respective interfaces, in particular the 3Dmodel m via a first interface i1. Further, a detail-state is provided onthe entity on which the application MDA is implemented or executed. Forproviding the detail-state several options do exist. In someembodiments, the detail-state is received via an interface from anexternal entity, e.g. directly from the client. In some embodiments, thedetail-state is calculated locally on the computing device, where themodel detailing application MDA is deployed. For this purpose, arequirement algorithm may be provided on the computing device 100. Therequirement algorithm is adapted to process context data of therespective receiving entity C for processing the 3D model m, rm′. Thecontext data are processed—e.g., by accessing the rules engine RE—inorder to calculate a detail-state as a set of requirements for operatingand executing the reduction algorithm. The context data may be receivedvia a second interface i2. The detailing application MDA first generatesa reference copy m′ of the received 3D model, represented in therespective 3D model data m and then applies the reduction algorithm onthe generated reference copy m′ for calculating the reduced referenceversion rm′, which is also a 3D model, but in an amended, modified,reduced or enriched version, dependent on the determined detail-stateand requirements of the receiving entity C acting as client. It iscalled ‘reduced reference model’ or ‘reduced reference version’. Thecalculated reduced reference version rm′ may then be transmitted via athird interface i3 to the respective client according to apre-determined transmission time interval or after a pre-determinedevent occurred. The third interface i3 may also be used to receive theoriginal model m.

In some embodiments, the CAD system accesses or receives the originalmodel m. By means of the model detailing application MDA functionswithin the CAD system are used to calculate a reduced reference versionrm′ of the original model m based on instructions of the model detailingapplication MDA, in particular by applying a reduction algorithm X2based on the detail-state. The detail-state may indicate a detail schemeto be used during reduction or amendment of the reduction algorithm X2.The detail-state may also be received via a user input on a userinterface. The process model is calculated as reduced reference modelrm′ and will be administered and managed centrally within the PLM systemand in relation to the original model m.

A typical workflow is explained below with respect to FIG. 4. AfterStart, in step S1 the 3D model data is received. In step S2 thedetail-state is provided. In step S1 context data may be received and instep S2 the rules engine RE may be accessed in order to calculate thedetail-state algorithmically, based on the received context data. Instep S3 the reduction algorithm is executed and in step S4 the reducedreference version rm′ of the 3D model is calculated and provided. Instep S5 the calculated reduced reference version rm′ is stored fortransmission to the clients C and/or for further analysis. Thus, themodel detailing application MDA is usually executed on a computing nodewith sufficient computing resources (processing/storage capacity etc.)and generates the reduced reference version rm′ of the original 3D modeland prepares the same for transmission to smart glasses AGR, which willbe described in more detail below with respect to FIG. 5 or for theother clients C.

FIG. 5 shows an example embodiment using smart glasses, e.g. augmentedreality glasses ARG. The augmented or virtual reality glasses ARG may beassociated to other receiving devices or entities C of the client, e.g.a beamer or a mobile device. The data exchange between the computingnode 100 on which the model detailing application MDA is deployed andthe smart glasses ARG is wireless. As depicted in FIG. 5 the reducedreference version rm′ is provided on a CAD system or PLM system.Relevant data, shown in FIG. 5 with reference numeral ‘rel’ of thereduced reference version rm′ are prepared for being transmitted to thesmart glasses ARG and may optionally and in addition be transmitted toat least one other receiving entity of the client as well, which isrepresented in FIG. 5 with the transmission path shown in dotted lines.‘Relevant data’ in this respect is to be construed as dedicatedlyselected data for the respective process step, which is to be executedon the receiving device C.

FIG. 6 shows another flow chart of the sequence of algorithmicexecutions according to an example embodiment. Context data cd areaccessed and processed by the requirement algorithm X1 in order tocalculate a detail-state y which is then forwarded with the referenceversion of the 3D model m′ to the reduction algorithm X2 in order toprocess the reduced reference version rm′ according to the requirementsof the detail-state.

While the teachings of the current disclosure have been described inrelation to various example embodiments, this description is forillustrative purposes only. For example, the computing node 100 or theprocessor P may be a personal computer, a server, a distributed systemor a local system or even a mobile computing device or another technicalapparatus, for example a smart glass, wherein the computing node 100 orthe processor P are equipped with resources to execute a CAD system andfunctions thereof. Processing of the 3D model on the respectivereceiving entities may have different technical purposes andfunctionality. For the person skilled in the art it is clear that theteachings may also be used for other services besides production, likeservice and maintenance of systems and sales. Also, the model detailingapplication MDA together with the CAD system needs not to be deployed asphysical application software. For example, it is also possible that theapplication functionality (reduction functionality) described above canbe hosted in a virtualized environment as well. Accordingly, the scopeof the teachings are not limited by the scope of the embodiments.

What is claimed is:
 1. Method for preparing a three-dimensional modelfor a fabrication component in the context of production for datatransmission to different receiving entities, the method comprising:receiving three-dimensional model data via an input interface; providinga detail-state for processing of the three-dimensional model on therespective receiving entity; and executing a reduction algorithm on areference version of the received three-dimensional model data forautomatically calculating and providing a reduced reference version withthe provided detail-state.
 2. Method according to claim 1, wherein: eachreceiving entity has an associated required detail-state; and providingcomprises: receiving context data specifying in which technical contextthe three-dimensional model will be used for processing on the receivingentity and accessing a rules engine with an associated rules databasewith the received context data to provide the detail-statealgorithmically, indicating a respective level of detail in which thereduction algorithm should be operated with.
 3. Method according toclaim 1, wherein the reduction algorithm deletes, adds, and/or modifiesdetermined elements in the reference version of the 3D model based onthe provided detail-state and all references to the determined elementsare deleted.
 4. Method according to claim 1, further comprising storingthe reduced reference version of the 3D model with a digital referenceto the 3D model.
 5. Method according to claim 1, wherein the contextdata specify a context and/or a functionality in which the 3D model isintended to be used on the receiving entity.
 6. Method according toclaim 1, further comprising providing the reduced reference version onsmart glasses of a receiving entity.
 7. Method according to claim 1,wherein the method is executed in a batch mode in a central managementsystem and/or in a local application.
 8. Method according to claim 1,further comprising comparing the reduced reference version to thethree-dimensional model.
 9. Method according to claim 1, wherein themethod is executed in a CAD system and the input interface comprises anAPI interface of the CAD-system which may access a second set offunctions of the CAD system.
 10. Reduction system for preparing athree-dimensional model for a fabrication component in the context ofproduction for data transmission to different receiving entities, thesystem—comprising: an input interface for receiving 3D model data; and aprocessor for providing a detail-state of a receiving entity forprocessing the three-dimensional model; wherein the processor isprogrammed to execute a reduction algorithm on a reference version ofthe received 3D model data for automatically calculating and providingat least one reduced reference version thereof with the provideddetail-state.
 11. (canceled)